|
|
#### Test : GTS #### Module : WvtsDeviceTestCases #### Test Case : com.google.android.wvts.MediaDrmParameterizedTests#testUsageTableCapacity[L1] #### run gts -m WvtsDeviceTestCases -t com.google.android.wvts.MediaDrmParameterizedTests#testUsageTableCapacity[L1] It was passed after factory reset, please skip this item. |
|
|
Hello, Kinbay, I will upload the fail items here until I get the full passed report, please help each item to pass. Thank you. Sangmin Choi. |
|
|
#### Test : TVTS #### Module : TvtsYouTubeTS #### Test Case : com.google.android.apps.yts.tvts.TvtsYouTubeTS#testYTS #### run tvts -m TvtsYouTubeTS -t com.google.android.apps.yts.tvts.TvtsYouTubeTS#testYTS It was passed. |
|
|
#### Test : CTS or CTS on GSI #### Module : CtsNetTestCases #### Test did not run. No token '[SIM_CARD]' matching it on any device. #### How can I pass this item? It was passed, you don't need to check this item. 스크린샷 2024-05-07 오후 1.59.41.png (50,684 bytes) |
|
|
#### Test : STS #### Module : CtsSecurityTestCases #### run sts-dynamic-full -m CtsSecurityTestCases It was passed after moved the focus. For the below case, you can try the UI focus on the bottom button (as attached screenshot) 05-13 12:13:27 I/ModuleListener: [1/100] SKBFX9C72AC android.security.cts.FlagSlipperyTest#testWindowIsNotSlipperyWhenAdded FAILURE: java.lang.AssertionError: Expected ACTION_MOVE, but got a null event instead at org.junit.Assert.fail(Assert.java:89) at android.security.cts.FlagSlipperyTestKt.assertAction(FlagSlipperyTest.kt:64) at android.security.cts.FlagSlipperyTestKt.access$assertAction(FlagSlipperyTest.kt:1) at android.security.cts.FlagSlipperyTest$assertBottomWindowDoesNotReceiveSlipperyTouch$1.perform(FlagSlipperyTest.kt:320) at android.security.cts.FlagSlipperyTest$assertBottomWindowDoesNotReceiveSlipperyTouch$1.perform(FlagSlipperyTest.kt:316) at androidx.test.core.app.ActivityScenario.lambda$onActivity$2$ActivityScenario(ActivityScenario.java:660) at androidx.test.core.app.ActivityScenario$$Lambda$4.run(Unknown Source:4) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:2266) at android.os.Handler.handleCallback(Handler.java:938) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.app.ActivityThread.main(ActivityThread.java:7839) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003) I got following fails under STS CtsSecurityTestCases. It's weird because I can get pass result last week, but now I couldn't pass it. Did you get same fail before? or do you have any guide to pass it? |
|
|
This is result and log for CtsSecurityTestCases. |
|
|
Hello, Kinbay, The security patch version of the firmware I'm testing is 2024-03-01. Can I use the android-sts-12_sts-r25-linux-arm.zip for security patch 2024-03-01? In the past, I could pass STS using android-sts-12_sts-r25-linux-arm.zip. At that time, the security patch version of the firmware was 2024-02-01. Thank you. Sangmin Choi. |
|
|
Hi Choi For the below case, you can try the UI focus on the bottom button (as attached screenshot) Test : STS Module : CtsSecurityTestCases Thank you Kinbay image.png (91,762 bytes) |
|
|
Hi Choi For the sts tools As I know the tools are not affected by the security patch Please check you are flash user debug image to test sts. Thank you Kinbay |
|
|
Hello, Kinbay, For the below case, you can try the UI focus on the bottom button (as attached screenshot) -> It works, I can get pass report of STS. Thank you. Sangmin Choi. |
|
|
Hello, Kinbay, I attached the Google xTS report which is tested by ALT. Please review the attached Google xTS report whether there is any issue to get the certification or not. There is no CTS Verifier report yet. Thank you. Sangmin Choi. |
|
|
Hello, Kinbay, Could you please check this comment in this ticket? https://btracker-cns.fii-foxconn.com/vaas/view.php?id=1938#c15809 Thank you. Sangmin Choi. |
|
|
Hi Choi I have reviewed the reports and found no issues. Thank you Kinbay |
|
|
Hello, Kinbay, Could you please check review the following Smoke Test Report? https://docs.google.com/spreadsheets/d/1bcExPEK2PqWqWCjVseCuuMm4MVeJUu9i/edit#gid=169765125 Thank you. Sangmin Choi. |
|
|
Hi Choi I have reviewed the report and found no issues. Thank you Kinbay |
|
|
Hello, Kinbay, Thank you for support. Best Regards, Sangmin Choi. |
|
|
Hello, Kinbay, Below item was passed before, but I can't get the pass report now. Do you have any experience like me? Could you please check your QA engineer? Test : CTS Module : CtsHdmiCecHostTestCases Test Case : android.hdmicec.cts.common.HdmiCecStartupTest run cts -s SKBFX9C72AF -m CtsHdmiCecHostTestCases -t android.hdmicec.cts.common.HdmiCecStartupTest Unexpected messages sent by the device expected to be empty but was: [0d, 8e] Thank you. Sangmin Choi. |
- yk.jung ( (ALTech) Younkwang Jung ) developer
.png)
